@jpwhite4

So I believe I've found the root problem that was causing this behavior. In \CCR\Logger.php::extractMessage starting at line 46:

 if (is_array($record)) {
   return json_encode($record);
}

This code is the reason that a PHP Warning about an Array to String conversion is thrown in CCRLineFormater::extractMessage on line 44 $nonMessageParts[] = "$key: $value";.

Here's an example:

Given the following logger call

$logger->info(array(
    'message'     => 'start',
    'action_name' => $actionName,
    'action'      => $actionObj,
    'start_date'  => $overseerOptions->getStartDate(),
    'end_date'    => $overseerOptions->getEndDate(),
));

the result of Logger::extractMessage looks like this:

{
   "message":"start",
   "action_name":"db-model-test.create-table",
   "action":{},
   "start_date":null,
   "end_date":null
}

Note the empty action object.

When this data get's to CCRLineFormatter::extractMessage as the value of $record['message']and is subsequently decoded on line 29 w/ json_decode($record['message'], true). The value of action is converted to an associative array due to the true argument passed to json_decode. Which ultimately is what causes the PHP Warning about converting an Array to string to be thrown on line 44.

So there's a couple of different ways I've thought of that we can fix this:

• One is obviously the way you've presented here which definitely works.
• Another would be to update Logger::extractMessage to look like this:

protected function extractMessage($record)
{
    if (is_array($record)) {
        while (list($key, $value) = each($record)) {
            if (is_object($value)) {
                $record[$key] = (string) $value;
            }
        }
        return json_encode($record);
    }
    return json_encode(array('message' => $record));
}

Thus making sure that we don't lose any information about objects that can be converted to strings.

• And the last way to resolve this would be to implement the JsonSerializable interface for the ETL Action classes which would make sure that they produce the expected output when used in conjunction with json_encode.

Thoughts?

@jpwhite4 So a quick update, I was going back through the PHP7 & MariaDB updates and it turns out that, when running on Centos8, I need to include the changes to Logger::extractMessage to make sure that the component tests pass.

The problem I ran into was when running the DBModelTest component tests they all would error out with SQLSTATE[42000]: Syntax error or access violation: 1049 Unknown database 'test'. The reason for this particular error is that the function ( BaseETLTest::executeEtlAction) used to execute an ETL action was directly constructing / executing an ETL action object as opposed to using the ETL Overseer. And we only get the automatically create db functionality if we execute actions / pipelines via the ETL Overseer. Once I updated this function to utilize the overseer I started getting our good 'ol friend Array to string converstion error. I'm guessing it threw an error as opposed to just a warning due to PHP7 being more restrictive by default than PHP5.4. But needless to say I was able to resolve these new errors with the changes I mentioned above.

This pull request is superseded by the #1493